home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ShareWare OnLine 2
/
ShareWare OnLine Volume 2 (CMS Software)(1993).iso
/
bbs_soft
/
sf33_2.zip
/
SF33DOCS.ZIP
/
SF-WIN.DOC
< prev
next >
Wrap
Text File
|
1993-03-03
|
5KB
|
100 lines
SF-WIN.DOC
Running SPITFIRE v3.3 with Windows 3.x
SPITFIRE - Version 3.3
Copyright (C) by Mike Woltz, 1987-1993
Buffalo Creek Software
RUNNING SPITFIRE WITH WINDOWS 3.X
---------------------------------
In order to run SPITFIRE v3.3 under MS Windows 3.X, Sysops need to
create a PIF (Program Information File). Windows uses PIFs to run DOS
applications. A PIF file tells Windows the name and the location of
the DOS (non-Windows application) program being run and describes the
necessary memory and hardware requirements. A PIF file is required
whether running a single node or a multi-node BBS.
To create a PIF file, Sysops must run the PIF editor which is
located in the Accessories Group.
Memory Requirements:
-------------------
Windows sets a MINIMUM value of 128K for all programs that it runs
via a PIF file. However, Windows assigns ALL available memory to all
PIF applications unless told to do otherwise. Even though SPITFIRE
normally requires more than 128K to run, you will probably not need
to increase this value.
Sysops who intend to drop to DOS from the SPITFIRE window and
are running in Real or Standard Mode could increase the memory
requirements. In 386 Enhanced Mode, a better way would be to open
another DOS window.
All other values are the Windows default PIF values. If running
Windows 3.X in 386 Enhanced Mode, click on ADVANCED options to examine
additional parameters and settings. It is not possible to see these
settings while running in Real or Standard Mode without pulling down
the Mode Option and select 386 Enhanced Mode. Enhanced options are
meaningless when running Windows in Real or Standard Modes. Under
Multitasking Options (ADVANCED), set both Background Priority and
Foreground Priority to 50 for more equitable sharing of time slices
between windows.
Hardware Requirements:
---------------------
To run multiple active SPITFIRE windows on the screen, Sysops MUST
run in 386 Enhanced Mode. This REQUIRES a 386SX or 386DX CPU. 2MB of
RAM is recommended, but the more the better! Sysops MUST install the
HIMEM.SYS driver that is included on the Windows 3.X diskettes
according to parameters applicable to their systems. The popular
QEMM386 program (Version 5.1 and greater) may be substituted for
HIMEM.SYS with appropriate parameters. Sysops should ideally be running
the SMARTDRV cache program as it is designed to work with Windows.
Remember to load ANSI.SYS in your CONFIG.SYS if ANSI graphics is
available on the BBS!
Sysops running the BBS on an 8086, 8088 or 80286 can run SPITFIRE
while running Windows, but it will NOT run in a window. It will
instead run in "exclusive mode", that is to say, full screen. When
switching back to the main Windows screen, SPITFIRE will "freeze"
(as will any other DOS application.) Running an application in this
manner is generally referred to as running "under" windows as opposed
to running "in" windows which refers to the 386 Enhanced "in a
window" style.
Additional Information:
----------------------
To run SPITFIRE v3.3 in a DOS window, select Background and Windowed
as options when creating your SPITFIRE PIF file. This will allow
viewing of one or several nodes on the screen at the same
time as well as other Windows applications. Background windows do not
"freeze" when you are running Windows in 386 Enhanced Mode.
If running a multi-node setup, it is suggested to name the batch
files and PIF files based upon their node number (SF1.BAT, SF1.PIF,
etc.) In addition, there are Windows applications which allow creation
of custom Icons which are unique for each node.
To load Windows automatically and have it bring up the SPITFIRE
window(s), first edit AUTOEXEC.BAT and have it run WIN.COM. Next,
edit WIN.INI, and set "RUN=SF1.BAT SF2.BAT", etc. to automatically
boot up all SPITFIRE nodes. Make sure to leave a space between all
items listed on the WIN.INI "RUN=" line. If running Windows 3.1 or
greater, all SF.BAT files can be placed in the StartUp Group which
will automatically run them when Windows 3.1 loads.
When configuring SPITFIRE to operate multi-node in the Windows
environment and when attempting to boot node 2 you incur a
runtime error 162, this is caused by having the DOS SHARE loaded
in memory. A runtime error 162 is hardware failure.